Restoring virtual network function (vnf) performance via vnf reset of lifecycle management

ABSTRACT

Techniques for identifying and remedying performance issues of Virtualized Network Functions (VNFs) are discussed. An example method includes outputting a request to a network Element Manager (EM) to create a Virtualized Network Function (VNF) Performance Measurement (PM) job to collect VNF PM data from a VNF and receiving a set of VNF PM data associated with the VNF from the EM. The set of VNF PM data is processed associated with the VNF. A request to the EM is output to create a Virtualization Resource (VR) PM job to collect, through a VNF Manager (VNFM) and a virtualized infrastructure manager (VIM), VR PM data from a VR used by the VNF. Then a set of VR PM data is received from the EM and processed.

REFERENCE TO RELATED APPLICATIONS

This application is a Continuation of U.S. application Ser. No.17/156,966 filed on Jan. 25, 2021, which is a Continuation of U.S.application Ser. No. 15/767,203 filed on Apr. 10, 2018, which is aNational Phase entry application of International Patent Application No.PCT/US2016/033002 filed May 18, 2016, which claims priority to U.S.Provisional Application 62/249,769 filed on Nov. 2, 2015, entitled“RESTORING VNF PERFORMANCE VIA VNF RESET OF LIFECYCLE MANAGEMENT” in thename of Joey Chou et al. and is hereby incorporated by reference in itsentirety.

FIELD

The present disclosure relates to wireless technology, and morespecifically to restoring performance of virtual network functions(VNFs) of a wireless network.

BACKGROUND

Network Function Virtualization (NFV) involves the replacement ofphysical network nodes with Virtual Network Functions (VNFs) implementedvia Virtualization Resources (VRs) that perform the same function as thephysical node.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a diagram illustrating a Performance Measurement (PM) datacollection flow that can be employed in connection with various aspectsdescribed herein.

FIG. 2 is a diagram illustrating an example flow of a VirtualizationResource (VR) performance data collection scenario according to variousaspects described herein.

FIG. 3 is a block diagram illustrating a system that facilitatesidentification and mitigation of performance issues at a VirtualizedNetwork Function (VNF) by a Network Manager (NM) according to variousaspects described herein.

FIG. 4 is a block diagram illustrating a system that facilitatescreation of Performance Measurement (PM) jobs for a VNF and anassociated VR and reporting of associated PM data according to variousaspects described herein.

FIG. 5 is a flow diagram illustrating a method that facilitatesdiagnosis and mitigation of VNF performance issues by a NM according tovarious aspects described herein.

FIG. 6 is a flow diagram illustrating a method that facilitatescollection and communication of PM data from a VNF and associated VR bya network Element Manager (EM) according to various aspects describedherein.

FIG. 7 is a block diagram illustrating an example user equipment (UE)useable in connection with various aspects described herein.

DETAILED DESCRIPTION

The present disclosure will now be described with reference to theattached drawing figures, wherein like reference numerals are used torefer to like elements throughout, and wherein the illustratedstructures and devices are not necessarily drawn to scale. As utilizedherein, terms “component,” “system,” “interface,” and the like areintended to refer to a computer-related entity, hardware, software(e.g., in execution), and/or firmware. For example, a component can be aprocessor (e.g., a microprocessor, a controller, or other processingdevice), a process running on a processor, a controller, an object, anexecutable, a program, a storage device, a computer, a tablet PC and/ora user equipment (e.g., mobile phone, etc.) with a processing device. Byway of illustration, an application running on a server and the servercan also be a component. One or more components can reside within aprocess, and a component can be localized on one computer and/ordistributed between two or more computers. A set of elements or a set ofother components can be described herein, in which the term “set” can beinterpreted as “one or more.”

Further, these components can execute from various computer readablestorage media having various data structures stored thereon such as witha module, for example. The components can communicate via local and/orremote processes such as in accordance with a signal having one or moredata packets (e.g., data from one component interacting with anothercomponent in a local system, distributed system, and/or across anetwork, such as, the Internet, a local area network, a wide areanetwork, or similar network with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry, in which the electric or electronic circuitry canbe operated by a software application or a firmware application executedby one or more processors. The one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components.

Use of the word exemplary is intended to present concepts in a concretefashion. As used in this application, the term “or” is intended to meanan inclusive “or” rather than an exclusive “or”. That is, unlessspecified otherwise, or clear from context, “X employs A or B” isintended to mean any of the natural inclusive permutations. That is, ifX employs A; X employs B; or X employs both A and B, then “X employs Aor B” is satisfied under any of the foregoing instances. In addition,the articles “a” and “an” as used in this application and the appendedclaims should generally be construed to mean “one or more” unlessspecified otherwise or clear from context to be directed to a singularform. Furthermore, to the extent that the terms “including”, “includes”,“having”, “has”, “with”, or variants thereof are used in either thedetailed description and the claims, such terms are intended to beinclusive in a manner similar to the term “comprising.”

As used herein, the term “circuitry” may refer to, be part of, orinclude an Application Specific Integrated Circuit (ASIC), an electroniccircuit, a processor (shared, dedicated, or group), and/or memory(shared, dedicated, or group) that execute one or more software orfirmware programs, a combinational logic circuit, and/or other suitablehardware components that provide the described functionality. In someembodiments, the circuitry may be implemented in, or functionsassociated with the circuitry may be implemented by, one or moresoftware or firmware modules. In some embodiments, circuitry may includelogic, at least partially operable in hardware.

Various embodiments described herein can facilitate improved performanceof Virtualized Network Functions (VNFs) via identification ofunderperforming VNFs and restoration of VNF performance.

The performance of an application software is tightly coupled to thehardware resource on which the application software is running. Forexample, this can be when a web application is running so slowly that itmay take minutes to display the web page that contains multimediacontent, such as pictures, video, audio, text, etc. When this happens, acommon response is to launch a task manager to see how the computerhardware is performing. The task manager can display the statistics ofCPU, memory, disc, and network (i.e. WiFi, or Ethernet) usages.

The following are a few example scenarios that can be found from thetask manager: (1) CPU 100%, memory 100%, network 70%, which may indicatethat the computer is using all its resources to process the multimediacontent; (2) CPU 10%, memory 40%, network 10%, which may indicate thatthe application server is too busy to provide the content on time; or(3) CPU 5%, memory 85%, network 30%, which may indicate that theapplication is pending on the availability of certain resources (e.g.,memory) that have been exhausted due to unknown reasons.

These different scenarios can result from different circumstances, eachof which can be analogous to scenarios that can occur in connection withNetwork Function Virtualization (NFV). Scenario 1 can indicate that thecomputer hardware is too old to handle the multimedia content, andprobably should be replaced. In NFV, a similar scenario can indicatethat the resource is deficient in handling the traffic, and can besolved by auto-scaling. Scenario 2 can indicate a server problem that isout of the control of any application. Scenario 3 can point to problemsin the application or operating system that can be triggered by manydifferent reasons. One common way to fix this problem is to simply pressthe reset button, as it is not worth spending effort to find out itsroot cause. A similar scenario can happen in NFV. Analogously, onepossible way to solve this problem is to restart the VNF via VNFtermination and re-instantiation, or via reset.

In various embodiments, techniques described herein can be employed tocorrelate both VNF performance measurements and Virtualization Resource(VR) measurements to discover a VNF that is not performing, and find asolution to mitigate the VNF.

Referring to FIG. 1, illustrated is a diagram of a PerformanceMeasurement (PM) data collection flow that can be employed in connectionwith various aspects described herein. The system illustrated in FIG. 1comprises a Network Manager (NM), Network Function Virtualization (NFV)Orchestrator (NFVO), network Element Manager (EM), a set of VirtualizedNetwork Functions (VNFs) virtualized by Virtualization Resources (VRs)of a NFV Infrastructure (NFVI), a VNF Manager (VNFM), and a VirtualizedInfrastructure Manager (VIM). The solid lines between these entitiesindicate the various reference points that facilitate data exchangebetween these entities, while the dashed and dotted lines indicate theflow of PM data (either VNF PM data or VR PM data).

To collect the PM data, the NM can create a PM job at the EM that candetermine which measurement types, on which measured resources, at whichtimes, are to be executed, which can be based on techniques discussed in3GPP (Third Generation Partnership Project) TS (Technical Specification)32.401.

Two types of PM data can be collected: VNF PM data, and VR PM data forthe VR(s) that implement that VNF.

For VNF PM data collection, the EM can request that VNF to collect theVNF PM data based on the schedule and time period provided by EM.

For VR PM data collection, the EM can create a VR PM job at the VNFMthat contains the measurement types, and the periods for which thecollection is to be performed. Then, the VNFM can create a VR PM job atthe VIM that contains the same information as received from the EM. TheVIM can request the NFVI to collect the VR PM data based on the scheduleand time period defined in the VR PM job.

VNF performance is tightly coupled to the performance of the VR used bythe VNF. Thus, when it is detected via monitoring the VNF performancemeasurements that the performance of a VNF is poor, a PM job can becreated to collect the performance measurements of the VR used by theVNF. The VNF related VR performance measurements can be analyzed todetermine whether to implement mitigation techniques. For example, ifthe VR performance measurements have some abnormal pattern (e.g. thememory usage is very high, but the CPU usage is very low), it mayindicate that the VNF application is pending on the availability of VR(e.g. memory) that have been exhausted due to unknown reasons. Tomitigate this problem, the VNF can be restarted, for example via VNFtermination/re-instantiation or via VNF reset.

Referring to FIG. 2, illustrated is an example flow of a VR performancedata collection scenario according to various aspects described herein.At 1, the NM can create a VNF PM job at the EM to request a VNF toreport the VNF PM data based on a schedule determined by the VNF PM job.At 2, the EM can receive the VNF PM data from the VNF. At 3, the EM canreport the VNF PM data to the NM. At 4, the NM can detect (e.g., via athreshold crossing mechanism, etc.) that the VNF performance has beenpoor, and can decide to create a VR PM job to collect the VR PM data. At5, the NM can create a VR PM job at the EM to collect the VR PM data. At6, the EM can create a VR PM job at the VNFM, based on the VR PM jobinformation (e.g., resource type, collection/reporting periods, etc.)received from the NM. At 7, the VNFM can create a VR PM job at the VIM,based on the VR PM job information received from the EM to collect VR PMdata. At 8, the VIM can receive the VR PM data from the NFVI thatgenerated the VR PM data at the schedule determined by the VR PM job. At9, the VIM can forward the VR PM data to the VNFM managing the VNF/VNFC(VNF component(s)). At 10, when the VNFM receives the VR PM data, it canidentify the VNF/VNFC where the VR is used, and can forward the data tothe EM managing the VNF/VNFC. At 11, the EM can report the VR PM data tothe NM. At 12, the NM can analyse the VNF PM data and the VNF related VRPM data, and can determine whether to restart the VNF. At 13, the NM cansend a request to the NFVO to terminate and re-instantiate the VNF, orto reset the VNF.

Referring to FIG. 3, illustrated is a block diagram of a system 300 thatfacilitates identification and mitigation of performance issues at a VNFby a Network Manager (NM) according to various aspects described herein.System 300 can include one or more processors 310, optional networkinterface controller (NIC) circuitry 320 (which can facilitatecommunication of data via one or more networks in some aspects), and amemory 330 (which can comprise any of a variety of storage mediums andcan store instructions and/or data associated with at least one of theone or more processors 310 or NIC circuitry 320). In various aspects,system 300 can be included within a NM of a communications network. Invarious aspects, system 400 can be included within an EM of acommunications network. In some aspects, the one or more processors 310,the NIC circuitry 320, and the memory 330 can be included in a singledevice, while in other aspects, they can be included in differentdevices, such as part of a distributed architecture. As described ingreater detail below, system 300 can facilitate creation of a VNF PM joband an associated VR PM job to diagnose performance issues associatedwith a VNF, and can request restarting of the VNF where appropriate.

Processor(s) 310 can determine characteristics for a VNF PM job to becreated at a network Element Manager (EM) (e.g., an EM employing system400, etc.) to collect PM data from a VNF. The VNF PM job can comprise aVNF PM job schedule, which can indicate what type of data to collectfrom the VNF, when VNF data is collected by the EM (e.g., every 5seconds, etc.), and when the EM reports VNF data to the NM (e.g., every60 seconds, etc.), etc. In aspects, some or all of this information canbe omitted, and default values can be employed. Processor(s) 310 cangenerate the VNF PM job and output a request to the EM to create the VNFPM job and collect VNF PM data according to the created VNF PM job(e.g., based at least in part on the VNF PM job schedule, etc.).

Processor(s) 310 can process VNF PM data associated with the VNF that isreceived from the EM, which can be collected and reported to the NMbased at least in part on the VNF PM job created at the EM (e.g.,according to the VNF PM job schedule, etc.). The processed VNF PM datacan be analyzed by processor(s) 310 to determine whether the VNF has oneor more performance issues. The analysis can be based on any of avariety of metrics or by comparison to one or more threshold values, andcan, in various aspects, depend on the nature of the network function(s)associated with the VNF.

In the event no negative performance issues are detected, processor(s)310 can continue monitoring and analyzing VNF PM data received from theEM until processor(s) 310 determine that the VNF has a negativeperformance issue. In response to processor(s) 310 determining that theVNF has a negative performance issue, processor(s) 310 can output arequest to the EM to generate a VR PM job to collect data from the VRutilized by the VNF. The request can indicate resources (e.g., VR(s))from which data is to be collected according to the VR PM job, alongwith the type(s) of data and/or measurements, when that data is to becollected and when that data is to be reported (e.g., which can both bedetermined via a VR PM schedule of the VR PM job), etc. In aspects, someor all of this information can be omitted, and default informationemployed instead. In other embodiment, the NM may decide to request EMto create a PM job to collect the VR PM data, prior to detectingnegative issues from the VNF PM data. The NM then analyzes and/orcorrelates both VNF PM data and VR PM data to determine whether thereare issues, and the actions to mitigate such issues.

Processor(s) 310 can receive VR PM data from the EM, which can be basedat least in part on the request to the EM to generate the VR PM (e.g.,of the indicated or default measurement type(s), from the VR resourcesindicated, according to the VR PM job schedule or a default schedule,etc.). Based on the VNF PM data and the VR PM data, processor(s) 310 candetermine whether to restart the VNF. This determination can be based onprocessor(s) 310 analyzing and/or correlating the VNF PM data and the VRPM data, and determining whether an abnormal VR usage pattern ispresent, for example, one of the scenarios described herein (e.g., lowprocessor usage (e.g., below a processing threshold, etc.)) coupled withhigh memory usage (e.g., above a memory threshold, etc.)). Ifprocessor(s) 310 detect an abnormal VR usage pattern, processor(s) 310can determine to restart the VNF. If processor(s) 310 do not detect anabnormal VR usage pattern, alternate determinations can be made (e.g.,to auto-scale the VR employed by the VNF if both processor and memoryusage are above threshold values associated with such a determination;to continue monitoring VNF PM data and/or VR PM data if a determinationis made that the VNF does not need to be restarted or assignedadditional resources, etc.).

Based on a determination to restart the VNF, processor(s) 310 cangenerate and output a request to the NFVO to restart the VNF (e.g., viareset, or termination/re-instantiation, etc.). In some aspects,processor(s) 310 can determine to reset the VNF, and the request torestart the VNF can be a request to reset the VNF. In other aspects,processor(s) 310 can determine to terminate and re-instantiate the VNF,and the request to restart the VNF can be a request to terminate andre-instantiate the VNF.

In some aspects, processor(s) 310 can communicate data (e.g., as inputor output) with other entities (e.g., the EM, the NFVO, etc.) via a NICassociated with NIC controller 320 (which can be associated with one ormore NICs), for example, when those entities are remote andcommunication occurs via one or more networks. In the same or otheraspects, processor(s) 310 can communicate data with these entities indistinct ways, such as via mutual access to a shared memory 330 or aportion thereof, etc.

Referring to FIG. 4, illustrated is a block diagram of a system 400 thatfacilitates creation of Performance Measurement (PM) jobs for a VNF andan associated VR and reporting of associated PM data according tovarious aspects described herein. System 400 can include one or moreprocessors 410, optional NIC circuitry 420 (which can facilitatecommunication of data via one or more networks in some aspects), andmemory 430 (which can comprise any of a variety of storage mediums andcan store instructions and/or data associated with at least one of theone or more processors 410 or NIC circuitry 420). In various aspects,system 400 can be included within an EM of a communications network. Insome aspects, the one or more processors 410, the NIC circuitry 420, andthe memory 430 can be included in a single device, while in otheraspects, they can be included in different devices, such as part of adistributed architecture. As described in greater detail below, system400 can facilitate collection of PM data from one or more VNFs and theVR(s) employed by those VNF(s) to report to a NM.

Processor(s) 410 can receive a VNF PM job from a NM (e.g., a NMemploying system 300, etc.). The VNF PM job can indicate a VNF tocollect data from, the type(s) of data to collect, and can also comprisea VNF PM job schedule, that can indicate when to collect data from theVNF, and when to report collected data (or, in various aspects, dataderived therefrom, such as averages, minima, maxima, etc.). In aspects,some or all of this information can be omitted, in which case defaultvalues can be employed. In one example embodiment, a VNF PM job schedulecan indicate that the EM should collect VNF PM data from the VNF every 5seconds (although greater or lesser times can be used in variousaspects, e.g., N ms or N s, where N is a positive integer), and reportVNF PM data to the NM every 60 seconds (although greater or lesser timescan be used in various aspects, e.g., N ms or N s, where N is a positiveinteger).

Processor(s) 410 can output one or more requests to the indicated VNF tocollect VNF PM data based on the VNF PM job (e.g., of the indicated ordefault type(s), according to the VNF PM job schedule, etc.), and canreceive the requested VNF PM data from the VNF. Processor(s) 410 canoutput to the NM the received VNF PM data, VNF PM data derived from thereceived VNF PM data (and potentially from one or more other sets ofreceived VNF PM data), or a combination thereof, at one or morereporting periods according to the VNF PM job schedule.

Processor(s) 410 can receive a request to create a VR PM job (e.g., afirst VR PM job) from the NM, and can create and process a VR PM job(e.g., the first VR PM job) based on the request, which can indicate aVR employed by the VNF, one or more measurement types, and a VR PMschedule that indicates when VR PM data is to be collected by the EM andwhen it is to be reported to the NM (or default values can be employed(e.g., measurement type(s), collection period(s), reporting period(s),etc.)). Based on the first VR PM job, processor(s) 410 can output asecond VR PM job, to the VNFM that allocated the VR to the VNF (whichcan create the second VR PM job at the VIM, to collect VR PM data fromthe allocated VR). Processor(s) 410 can receive the VR PM data from theVNFM (which receives it from the allocated VR via the VIM, which can beof the indicated or default measurement type(s) and according to the VRPM job schedule of the second VR PM job (which can indicate when VR PMdata is reported to the EM, and can be the same or a different schedulethan that of the first VR PM job, e.g., such that the EM receives VR PMdata more frequently than it reports VR PM data, etc.). Processor(s) 410can output to the NM the VR PM data (and/or data derived therefrom,etc.), which can be output to the NM based on the VR PM job schedule ofthe first VR PM job.

In some aspects, processor(s) 410 can communicate data (e.g., as inputor output) with other entities (e.g., the NM, the VNF, the VNFM, etc.)via a NIC associated with NIC controller 420 (which can be associatedwith one or more NICs), for example, when those entities are remote andcommunication occurs via one or more networks. In the same or otheraspects, processor(s) 410 can communicate data with these entities indistinct ways, such as via mutual access to a shared memory 430 or aportion thereof, etc.

Referring to FIG. 5, illustrated is a flow diagram of a method 500 thatfacilitates diagnosis and mitigation of VNF performance issues by a NMaccording to various aspects described herein. In some aspects, method500 can be performed at a NM. In other aspects, a machine readablemedium can store instructions associated with method 500 that, whenexecuted, can cause a NM to perform the acts of method 500.

At 510, a VNF PM job can be generated that can indicate a VNF that VNFPM data is to be collected from, measurement type(s), and can comprise aVNF PM job schedule that indicates collection and reporting periods forthe VNF PM data.

At 520, a request can be output to an EM to create the VNF PM job andcollect VNF PM data according to the VNF PM job.

At 530, VNF PM data can be received from the EM according to the VNF PMjob schedule.

At 540, a determination can be made as to whether there is a negativeperformance issue associated with the VNF based on comparison of the VNFPM data with one or more VNF PM thresholds.

At 550, in response to at least one of the VNF PM thresholds beingcrossed, a VR PM job can be created that can indicate what resource(s)(e.g., which VR) data is to be collected from, what measurement type(s)are to be collected, when VR PM data is to be collected, and when VR PMdata is to be reported (or default values can apply if not explicitlyindicated).

At 560, a request can be output to the EM to create the VR PM job (andthe EM can request the VNFM that allocated the VR to the VNF to createthe VR PM job or a second VR PM job based on the VR PM job, to obtain VRPM data from the VR via the VIM).

At 570, VR PM data can be received from the EM based on the VR PM jobschedule.

At 580, a determination can be made as to whether there is an abnormalVR usage pattern (e.g., high memory usage (e.g., above a memorythreshold) coupled with low processor usage (e.g., below a processorthreshold), etc.) associated with the VNF, which can be based oncorrelation and/or analysis of the VNF PM data and the VR PM data.

At 590, based on a determination that there is an abnormal VR usagepattern associated with the VNF, a request can be output to the NFVO torestart the VNF (e.g., reset the VNF, or terminate and re-instantiatethe VNF).

Referring to FIG. 6, illustrated is a flow diagram of a method 600 thatfacilitates collection and communication of PM data from a VNF andassociated VR by an EM according to various aspects described herein. Insome aspects, method 600 can be performed at an EM. In other aspects, amachine readable medium can store instructions associated with method600 that, when executed, can cause an EM to perform the acts of method600.

At 610, a VNF PM job can be received from an NM. The VNF PM job canindicate one or more of a VNF to collect data from, measurement type(s)of the VNF PM data, collection period(s) for collecting VNF PM data fromthe VNF, or reporting period(s) for reporting VNF PM data to the NM(reporting and collection period(s) can be indicated via a VNF PM jobschedule of the VNF PM job).

At 620, VNF PM data can be collected from the VNF based on the VNF PMjob (e.g., based on collection period(s) indicated via the VNF PM jobschedule of the VNF PM job, etc.).

At 630, VNF PM data can be output to the NM based on the VNF PM job(e.g., based on reporting period(s) indicated via the VNF PM jobschedule of the VNF PM job, etc.). The output VNF PM data can comprisecollected VNF PM data from one or more collection periods, data derivedfrom collected VNF PM data, or a combination thereof.

At 640, a request can be received from the NM to create a VR PM job. Therequest can indicate one or more of a VR to collect the data from (e.g.,the VR utilized by the VNF), measurement type(s) of data to becollected, collection period(s) to receive VR PM data from the VNFM thatallocated the VR, or reporting period(s) to report data to the NM(reporting and collection period(s) can be indicated via a VR PM jobschedule of the VR PM job).

At 650, a request to create a VR PM job can be output to the VNFM thatallocated the VR. The output request can indicate information indicatedvia the received request, or can be associated with distinct information(e.g., different collection and reporting period(s), etc.).

At 660, VR PM data can be received from the VNFM (which received the VRPM data from the VR via the VIM) based on the VR PM job schedule.

At 670, the VR PM data can be output to the NM based on the VR PM job(e.g., based on reporting period(s) indicated via the VR PM job scheduleof the VR PM job, etc.). The output VR PM data can comprise collected VRPM data from one or more collection periods, data derived from collectedVR PM data, or a combination thereof.

The tables below indicate example use cases of VNF PM data and VR PMdata in connection with various aspects described herein. Table 1,below, shows an example use case of VNF related VR performancemeasurements:

TABLE 1 Use Case of VNF related VR performance measurements <<Use>> Usecase Related stage Evolution/Specification use Goal The goal is for NMto collect the VNF related VR performance measurements that can beanalysed to understand the cause of poor VNF performance. For example,if the CPU usage is low, but, the memory usage is very high (e.g. 90%),it may indicate that the VNF application is pending on the availabilityof certain resources (e.g. memory). Actors and NM receives theperformance measurements. Roles EM reports the performance measurements.VNFM reports the VR PM data. VIM reports the VR performancemeasurements. NFVI produces the VR PM data. Telecom NM, EM, VNFM, VIM,NFVI resources Assumptions The VNF instance is in operation, and isusing the VR allocated to the VNF instance. Pre- Appropriate PM jobshave been scheduled to report the conditions VNF related VR PM data.Begins when NFVI generates a VR PM data. Act 1 (M) VIM collects the VRPM data from NFVI, and reports the data to the correct VNFM managing thesubject VNF/VNFC that utilizes the VRs. Act 2 (M) VNFM identifiesVNF/VNFC that utilizes the VR where the PM data is generated, andforwards the VR PM data to EM managing the subject VNF/VNFC. Act 3 (M)EM forwards the VNF related VR PM data to NM. Ends when NM receives theVNF related VR PM data. (*) Exceptions Post- NM may restart the VNF viaVNF termination/instantiation, conditions or reset. Traceability (*)

Table 2, below, shows an example use case of mitigating a VNFperformance bottleneck:

TABLE 2 Use Case of mitigating VNF performance bottleneck <<Use>> Usecase Related stage Evolution/Specification use Goal To mitigate the VNFperformance bottleneck. Actors and 3GPP management system. Roles TelecomNFV-MANO [NFV Management and Orchestration] resources VNF Assumptions3GPP management system is set up to collect VNF performance measurementsand NFV-MANO is set up to collect VNF-related virtualized resourceperformance measurements. Pre- VNF application threshold crossingtrigger and VNF-related conditions virtualized resource thresholdcrossing trigger have been set up by corresponding system(s) (i.e., 3GPPmanagement system or NFV-MANO system). Begins when The VNF performancemeasurement report(s), VNF-related virtualized resource performancemeasurement report(s) or the thresholds crossing alarm(s) are generated.Act 1 (M) 3GPP management system receives the VNF performancemeasurement report(s), VNF-related virtualized resource performancemeasurement report(s) or the thresholds crossing alarm(s). Act 2 (M)3GPP management system decides to optimize the VNF performance andmitigate the VNF performance bottleneck. Act 3 (M) 3GPP managementsystem requests VNF LCM [Lifecycle Management] operation (e.g.expansion) towards NFV- MANO. Ends when NFV-MANO executes the VNF LCMoperation. (*) Exceptions One of the acts identified above fails. Post-The VNF performance bottleneck has been mitigated after conditions theVNF LCM operation. Traceability REQ-NFV_PM_SYS-CON-3 (*)

In various aspects, embodiments described herein can be employed inconnection with a communications network that comprises one or moreradio access networks (RANs) that facilitate wireless communicationswith or between one or more user equipments (UEs). The following is adescription of an example UE that can be employed in connection withsuch a RAN.

Embodiments described herein may be implemented into a system using anysuitably configured hardware and/or software. FIG. 7 illustrates, forone embodiment, example components of a User Equipment (UE) device 700.In some embodiments, the UE device 700 may include application circuitry702, baseband circuitry 704, Radio Frequency (RF) circuitry 706,front-end module (FEM) circuitry 708 and one or more antennas 710,coupled together at least as shown.

The application circuitry 702 may include one or more applicationprocessors. For example, the application circuitry 702 may includecircuitry such as, but not limited to, one or more single-core ormulti-core processors. The processor(s) may include any combination ofgeneral-purpose processors and dedicated processors (e.g., graphicsprocessors, application processors, etc.). The processors may be coupledwith and/or may include memory/storage and may be configured to executeinstructions stored in the memory/storage to enable various applicationsand/or operating systems to run on the system.

The baseband circuitry 704 may include circuitry such as, but notlimited to, one or more single-core or multi-core processors. Thebaseband circuitry 704 may include one or more baseband processorsand/or control logic to process baseband signals received from a receivesignal path of the RF circuitry 706 and to generate baseband signals fora transmit signal path of the RF circuitry 706. Baseband circuitry 704may interface with the application circuitry 702 for generation andprocessing of the baseband signals and for controlling operations of theRF circuitry 706. For example, in some embodiments, the basebandcircuitry 704 may include a second generation (2G) baseband processor704 a, third generation (3G) baseband processor 704 b, fourth generation(4G) baseband processor 704 c, and/or other baseband processor(s) 704 dfor other existing generations, generations in development or to bedeveloped in the future (e.g., fifth generation (5G), 6G, etc.). Thebaseband circuitry 704 (e.g., one or more of baseband processors 704a-d) may handle various radio control functions that enablecommunication with one or more radio networks via the RF circuitry 706.The radio control functions may include, but are not limited to, signalmodulation/demodulation, encoding/decoding, radio frequency shifting,etc. In some embodiments, modulation/demodulation circuitry of thebaseband circuitry 704 may include Fast-Fourier Transform (FFT),precoding, and/or constellation mapping/demapping functionality. In someembodiments, encoding/decoding circuitry of the baseband circuitry 704may include convolution, tail-biting convolution, turbo, Viterbi, and/orLow Density Parity Check (LDPC) encoder/decoder functionality.Embodiments of modulation/demodulation and encoder/decoder functionalityare not limited to these examples and may include other suitablefunctionality in other embodiments.

In some embodiments, the baseband circuitry 704 may include elements ofa protocol stack such as, for example, elements of an evolved universalterrestrial radio access network (EUTRAN) protocol including, forexample, physical (PHY), media access control (MAC), radio link control(RLC), packet data convergence protocol (PDCP), and/or radio resourcecontrol (RRC) elements. A central processing unit (CPU) 704 e of thebaseband circuitry 704 may be configured to run elements of the protocolstack for signaling of the PHY, MAC, RLC, PDCP and/or RRC layers. Insome embodiments, the baseband circuitry may include one or more audiodigital signal processor(s) (DSP) 704 f. The audio DSP(s) 704 f may beinclude elements for compression/decompression and echo cancellation andmay include other suitable processing elements in other embodiments.Components of the baseband circuitry may be suitably combined in asingle chip, a single chipset, or disposed on a same circuit board insome embodiments. In some embodiments, some or all of the constituentcomponents of the baseband circuitry 704 and the application circuitry702 may be implemented together such as, for example, on a system on achip (SOC).

In some embodiments, the baseband circuitry 704 may provide forcommunication compatible with one or more radio technologies. Forexample, in some embodiments, the baseband circuitry 704 may supportcommunication with an evolved universal terrestrial radio access network(EUTRAN) and/or other wireless metropolitan area networks (WMAN), awireless local area network (WLAN), a wireless personal area network(WPAN). Embodiments in which the baseband circuitry 704 is configured tosupport radio communications of more than one wireless protocol may bereferred to as multi-mode baseband circuitry.

RF circuitry 706 may enable communication with wireless networks usingmodulated electromagnetic radiation through a non-solid medium. Invarious embodiments, the RF circuitry 706 may include switches, filters,amplifiers, etc. to facilitate the communication with the wirelessnetwork. RF circuitry 706 may include a receive signal path which mayinclude circuitry to down-convert RF signals received from the FEMcircuitry 708 and provide baseband signals to the baseband circuitry704. RF circuitry 706 may also include a transmit signal path which mayinclude circuitry to up-convert baseband signals provided by thebaseband circuitry 704 and provide RF output signals to the FEMcircuitry 708 for transmission.

In some embodiments, the RF circuitry 706 may include a receive signalpath and a transmit signal path. The receive signal path of the RFcircuitry 706 may include mixer circuitry 706 a, amplifier circuitry 706b and filter circuitry 706 c. The transmit signal path of the RFcircuitry 706 may include filter circuitry 706 c and mixer circuitry 706a. RF circuitry 706 may also include synthesizer circuitry 706 d forsynthesizing a frequency for use by the mixer circuitry 706 a of thereceive signal path and the transmit signal path. In some embodiments,the mixer circuitry 706 a of the receive signal path may be configuredto down-convert RF signals received from the FEM circuitry 708 based onthe synthesized frequency provided by synthesizer circuitry 706 d. Theamplifier circuitry 706 b may be configured to amplify thedown-converted signals and the filter circuitry 706 c may be a low-passfilter (LPF) or band-pass filter (BPF) configured to remove unwantedsignals from the down-converted signals to generate output basebandsignals. Output baseband signals may be provided to the basebandcircuitry 704 for further processing. In some embodiments, the outputbaseband signals may be zero-frequency baseband signals, although thisis not a requirement. In some embodiments, mixer circuitry 706 a of thereceive signal path may comprise passive mixers, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the mixer circuitry 706 a of the transmit signalpath may be configured to up-convert input baseband signals based on thesynthesized frequency provided by the synthesizer circuitry 706 d togenerate RF output signals for the FEM circuitry 708. The basebandsignals may be provided by the baseband circuitry 704 and may befiltered by filter circuitry 706 c. The filter circuitry 706 c mayinclude a low-pass filter (LPF), although the scope of the embodimentsis not limited in this respect.

In some embodiments, the mixer circuitry 706 a of the receive signalpath and the mixer circuitry 706 a of the transmit signal path mayinclude two or more mixers and may be arranged for quadraturedownconversion and/or upconversion respectively. In some embodiments,the mixer circuitry 706 a of the receive signal path and the mixercircuitry 706 a of the transmit signal path may include two or moremixers and may be arranged for image rejection (e.g., Hartley imagerejection). In some embodiments, the mixer circuitry 706 a of thereceive signal path and the mixer circuitry 706 a may be arranged fordirect downconversion and/or direct upconversion, respectively. In someembodiments, the mixer circuitry 706 a of the receive signal path andthe mixer circuitry 706 a of the transmit signal path may be configuredfor super-heterodyne operation.

In some embodiments, the output baseband signals and the input basebandsignals may be analog baseband signals, although the scope of theembodiments is not limited in this respect. In some alternateembodiments, the output baseband signals and the input baseband signalsmay be digital baseband signals. In these alternate embodiments, the RFcircuitry 706 may include analog-to-digital converter (ADC) anddigital-to-analog converter (DAC) circuitry and the baseband circuitry704 may include a digital baseband interface to communicate with the RFcircuitry 706.

In some dual-mode embodiments, a separate radio IC circuitry may beprovided for processing signals for each spectrum, although the scope ofthe embodiments is not limited in this respect.

In some embodiments, the synthesizer circuitry 706 d may be afractional-N synthesizer or a fractional N/N+1 synthesizer, although thescope of the embodiments is not limited in this respect as other typesof frequency synthesizers may be suitable. For example, synthesizercircuitry 706 d may be a delta-sigma synthesizer, a frequencymultiplier, or a synthesizer comprising a phase-locked loop with afrequency divider.

The synthesizer circuitry 706 d may be configured to synthesize anoutput frequency for use by the mixer circuitry 706 a of the RFcircuitry 706 based on a frequency input and a divider control input. Insome embodiments, the synthesizer circuitry 706 d may be a fractionalN/N+1 synthesizer.

In some embodiments, frequency input may be provided by a voltagecontrolled oscillator (VCO), although that is not a requirement. Dividercontrol input may be provided by either the baseband circuitry 704 orthe applications circuitry 702 depending on the desired outputfrequency. In some embodiments, a divider control input (e.g., N) may bedetermined from a look-up table based on a channel indicated by theapplications circuitry 702.

Synthesizer circuitry 706 d of the RF circuitry 706 may include adivider, a delay-locked loop (DLL), a multiplexer and a phaseaccumulator. In some embodiments, the divider may be a dual modulusdivider (DMD) and the phase accumulator may be a digital phaseaccumulator (DPA). In some embodiments, the DMD may be configured todivide the input signal by either N or N+1 (e.g., based on a carry out)to provide a fractional division ratio. In some example embodiments, theDLL may include a set of cascaded, tunable, delay elements, a phasedetector, a charge pump and a D-type flip-flop. In these embodiments,the delay elements may be configured to break a VCO period up into Ndequal packets of phase, where Nd is the number of delay elements in thedelay line. In this way, the DLL provides negative feedback to helpensure that the total delay through the delay line is one VCO cycle.

In some embodiments, synthesizer circuitry 706 d may be configured togenerate a carrier frequency as the output frequency, while in otherembodiments, the output frequency may be a multiple of the carrierfrequency (e.g., twice the carrier frequency, four times the carrierfrequency) and used in conjunction with quadrature generator and dividercircuitry to generate multiple signals at the carrier frequency withmultiple different phases with respect to each other. In someembodiments, the output frequency may be a LO frequency (fLO). In someembodiments, the RF circuitry 706 may include an IQ/polar converter.

FEM circuitry 708 may include a receive signal path which may includecircuitry configured to operate on RF signals received from one or moreantennas 710, amplify the received signals and provide the amplifiedversions of the received signals to the RF circuitry 706 for furtherprocessing. FEM circuitry 708 may also include a transmit signal pathwhich may include circuitry configured to amplify signals fortransmission provided by the RF circuitry 706 for transmission by one ormore of the one or more antennas 710.

In some embodiments, the FEM circuitry 708 may include a TX/RX switch toswitch between transmit mode and receive mode operation. The FEMcircuitry may include a receive signal path and a transmit signal path.The receive signal path of the FEM circuitry may include a low-noiseamplifier (LNA) to amplify received RF signals and provide the amplifiedreceived RF signals as an output (e.g., to the RF circuitry 706). Thetransmit signal path of the FEM circuitry 708 may include a poweramplifier (PA) to amplify input RF signals (e.g., provided by RFcircuitry 706), and one or more filters to generate RF signals forsubsequent transmission (e.g., by one or more of the one or moreantennas 710.

In some embodiments, the UE device 700 may include additional elementssuch as, for example, memory/storage, display, camera, sensor, and/orinput/output (I/O) interface.

Additionally, although the above example discussion of device 700 is inthe context of a UE device, in various aspects, a similar device can beemployed in connection with a base station (BS) such as an Evolved NodeB(eNB).

Examples herein can include subject matter such as a method, means forperforming acts or blocks of the method, at least one machine-readablemedium including executable instructions that, when performed by amachine (e.g., a processor with memory, an application-specificintegrated circuit (ASIC), a field programmable gate array (FPGA), orthe like) cause the machine to perform acts of the method or of anapparatus or system for concurrent communication using multiplecommunication technologies according to embodiments and examplesdescribed.

Example 1 is an apparatus configured to be employed within a NetworkManager (NM), comprising one or more processors configured to: output arequest to a network Element Manager (EM) to create a VirtualizedNetwork Function (VNF) PM job to collect VNF Performance Measurement(PM) data; process a set of Virtualized Network Function (VNF) PM dataassociated with a VNF, wherein the set of VNF PM data is received fromthe EM; output a request to the EM to create a Virtualization Resource(VR) PM job to collect VR PM data from a VR used by the VNF; process aset of VR PM data received from the EM; make a determination whether torestart the VNF, based on the processed set of VR PM data and theprocessed set of VNF PM data; and output a request to a network functionvirtualization orchestrator (NFVO) to restart the VNF based on adetermination to restart the VR.

Example 2 comprises the subject matter of any variation of example 1,wherein the one or more processors are further configured to make adetermination whether the VNF has a negative performance issue, based onthe processed set of VNF PM data, wherein the request to the EM tocreate the VR PM job is based on a determination that the VNF has thenegative performance issue.

Example 3 comprises the subject matter of any variation of example 1,wherein the one or more processors are configured to make thedetermination whether the VNF has the negative performance issue basedon one or more comparisons between the set of VNF PM data and one ormore VNF PM thresholds.

Example 4 comprises the subject matter of any variation of any ofexamples 1-3, wherein the one or more processors are further configuredto: analyze the set of VNF PM data and the set of VR PM data; make adetermination whether an abnormal VR usage pattern is detected based onthe analyzed set of VNF PM data and the analyzed set of VR PM data; andmake the determination whether to restart the VNF based on thedetermination being made that the abnormal VR usage pattern is detected.

Example 5 comprises the subject matter of any variation of any ofexamples 1-3, wherein the abnormal VR usage pattern comprises aprocessor usage below a processing threshold and a memory usage above amemory threshold.

Example 6 comprises the subject matter of any variation of any ofexamples 1-3, wherein the one or more processors are further configuredto: generate a VNF PM job associated with the VNF, wherein the VNF PMjob comprises a VNF PM job schedule; and output a request to the EM tocreate the VNF PM job, wherein the set of VNF PM data is received fromthe EM based on the VNF PM job schedule.

Example 7 comprises the subject matter of any variation of any ofexamples 1-3, wherein the VR PM job designates a resource type thatindicates the VR from which the VR PM data is to be collected.

Example 8 comprises the subject matter of any variation of any ofexamples 1-3, wherein the VR PM job designates a collection period thatindicates when the VR PM data is to be collected.

Example 9 comprises the subject matter of any variation of any ofexamples 1-3, wherein the VR PM job designates one or more reportingperiods that indicate when the VR PM data is to be reported to the NM.

Example 10 comprises the subject matter of any variation of any ofexamples 1-3, wherein the VR PM job indicates one or more measurementtypes to be collected, wherein the set of VR PM data comprises data ofthe one or more indicated measurement types.

Example 11 comprises the subject matter of any variation of any ofexamples 1-3, wherein the determination to restart the VNF is adetermination to terminate and re-instantiate the VNF, and wherein therequest to restart the VNF is a request to terminate and re-instantiatethe VNF.

Example 12 comprises the subject matter of any variation of any ofexamples 1-3, wherein the determination to restart the VNF is adetermination to reset the VNF, and wherein the request to restart theVNF is a request to reset the VNF.

Example 13 comprises the subject matter of any variation of any ofexamples 1-2, wherein the one or more processors are configured to makethe determination whether the VNF has the negative performance issuebased on one or more comparisons between the set of VNF PM data and oneor more VNF PM thresholds.

Example 14 comprises the subject matter of any variation of any ofexamples 1-2 or 13, wherein the one or more processors are furtherconfigured to: analyze the set of VNF PM data and the set of VR PM data;make a determination whether an abnormal VR usage pattern is detectedbased on the analyzed set of VNF PM data and the analyzed set of VR PMdata; and make the determination whether to restart the VNF based on thedetermination being made that the abnormal VR usage pattern is detected.

Example 15 comprises the subject matter of any variation of any ofexamples 1-2 or 13-14, wherein the abnormal VR usage pattern comprises aprocessor usage below a processing threshold and a memory usage above amemory threshold.

Example 16 comprises the subject matter of any variation of any ofexamples 1-2 or 13-15, wherein the one or more processors are furtherconfigured to: generate a VNF PM job associated with the VNF, whereinthe VNF PM job comprises a VNF PM job schedule; and output a request tothe EM to create the VNF PM job, wherein the set of VNF PM data isreceived from the EM based on the VNF PM job schedule.

Example 17 comprises the subject matter of any variation of any ofexamples 1-2 or 13-16, wherein the VR PM job designates one or more of aresource type that indicates the VR from which the VR PM data is to becollected, a collection period that indicates when the VR PM data is tobe collected, one or more reporting periods that indicate when the VR PMdata is to be reported to the NM, or one or more measurement types to becollected and wherein the set of VR PM data comprises data of the one ormore indicated measurement types.

Example 18 comprises the subject matter of any variation of any ofexamples 1-2 or 13-17, wherein the determination to restart the VNF is adetermination to terminate and re-instantiate the VNF, and wherein therequest to restart the VNF is a request to terminate and re-instantiatethe VNF.

Example 19 comprises the subject matter of any variation of any ofexamples 1-2 or 13-17, wherein the determination to restart the VNF is adetermination to reset the VNF, and wherein the request to restart theVNF is a request to reset the VNF.

Example 20 comprises the subject matter of any variation of example 1,wherein the one or more processors are further configured to: analyzethe set of VNF PM data and the set of VR PM data; make a determinationwhether an abnormal VR usage pattern is detected based on the analyzedset of VNF PM data and the analyzed set of VR PM data; and make thedetermination whether to restart the VNF based on the determinationbeing made that the abnormal VR usage pattern is detected.

Example 21 comprises the subject matter of any variation of example 1,wherein the abnormal VR usage pattern comprises a processor usage belowa processing threshold and a memory usage above a memory threshold.

Example 22 comprises the subject matter of any variation of example 1,wherein the one or more processors are further configured to: generate aVNF PM job associated with the VNF, wherein the VNF PM job comprises aVNF PM job schedule; and output a request to the EM to create the VNF PMjob, wherein the set of VNF PM data is received from the EM based on theVNF PM job schedule.

Example 23 comprises the subject matter of any variation of example 1,wherein the VR PM job designates a resource type that indicates the VRfrom which the VR PM data is to be collected.

Example 24 comprises the subject matter of any variation of example 1,wherein the VR PM job designates a collection period that indicates whenthe VR PM data is to be collected.

Example 25 comprises the subject matter of any variation of example 1,wherein the VR PM job designates one or more reporting periods thatindicate when the VR PM data is to be reported to the NM.

Example 26 comprises the subject matter of any variation of example 1,wherein the VR PM job indicates one or more measurement types to becollected, wherein the set of VR PM data comprises data of the one ormore indicated measurement types.

Example 27 comprises the subject matter of any variation of example 1,wherein the determination to restart the VNF is a determination toterminate and re-instantiate the VNF, and wherein the request to restartthe VNF is a request to terminate and re-instantiate the VNF.

Example 28 comprises the subject matter of any variation of example 1,wherein the determination to restart the VNF is a determination to resetthe VNF, and wherein the request to restart the VNF is a request toreset the VNF.

Example 29 is a machine readable medium comprising instructions that,when executed, cause a Network Manager (NM) to: generate a VirtualizedNetwork Function (VNF) Performance Management (PM) job associated with afirst VNF, wherein the VNF PM job comprises a VNF PM schedule; output arequest to an Element Manager (EM) to create the VNF PM job; receive aset of VNF PM data from the EM according to the VNF PM schedule;generate a Virtualization Resource (VR) PM job comprising a VR PMschedule, wherein the VR PM job is associated with a VR of the VNF;output a request to the EM to create the VRM PM job; receive a set of VRPM data from the EM according to the VR PM schedule; make adetermination whether an abnormal VR usage pattern is present based onan analysis of the set of VNF PM data and the set of VR PM data; andoutput to a Network Function Virtualization Orchestrator (NFVO) arequest to restart the VNF based on a determination that the abnormal VRusage pattern is present.

Example 30 comprises the subject matter of any variation of example 29,wherein the instructions, when executed, further cause the NM to comparethe set of VNF PM data to one or more VNF PM thresholds to determinewhether the one or more VNF PM thresholds have been crossed, wherein theVR PM job is generated based on a determination that at least one of theone or more VNF PM thresholds has been crossed.

Example 31 comprises the subject matter of any variation of example 29,wherein the VR PM job indicates a resource type of the VR, a collectionperiod of the VR PM schedule, and one or more reporting periods of theVR PM schedule, wherein the set of VR PM data is received from the EM inaccordance with the one or more reporting periods.

Example 32 comprises the subject matter of any variation of any ofexamples 29-31, wherein the request to restart the VNF comprises arequest to terminate and re-instantiate the VNF.

Example 33 comprises the subject matter of any variation of any ofexamples 29-31, wherein the request to restart the VNF comprises arequest to reset the VNF.

Example 34 comprises the subject matter of any variation of example 29,wherein the request to restart the VNF comprises a request to terminateand re-instantiate the VNF.

Example 35 comprises the subject matter of any variation of example 29,wherein the request to restart the VNF comprises a request to reset theVNF.

Example 36 is an apparatus configured to be employed within a networkElement Manager (EM), comprising one or more processors configured to:process a Virtualized Network Function (VNF) Performance Measurement(PM) job associated with a VNF, wherein the VNF PM job is received froma Network Manager (NM); output a request to the VNF to collect a firstset of VNF PM data based on the VNF PM job; receive the first set of VNFPM data from the VNF in response to the request to the VNF; output tothe NM a second set of VNF PM data based on the first set of VNF PMdata; process a first Virtualization Resource (VR) PM job associatedwith a VR of the VNF, wherein the VR PM job is received from the NM andbased on the set of VNF PM data; generate a second VR PM job based onthe first VR PM job; output the second VR PM to a VNF Manager (VNFM)that allocated the VR to the VNF; receive a first set of VR PM data fromthe VNFM; and output to the NM a second set of VR PM data based on thefirst set of VR PM data.

Example 37 comprises the subject matter of any variation of example 36,wherein the first VR PM job and the second VR PM job each indicate oneor more measurement types to be collected, wherein each of the first andthe second set of VR PM data comprises data of the one or more indicatedmeasurement types.

Example 38 comprises the subject matter of any variation of any ofexamples 36-37, wherein the first VR PM job comprises a first VR PMschedule and the second VR PM job comprises a second VR PM schedule.

Example 39 comprises the subject matter of any variation of example 38,wherein the first VR PM schedule and the second VR PM schedule eachdefine a collection period that indicates when the VR PM data is to becollected.

Example 40 comprises the subject matter of any variation of example 38,wherein the second VR PM schedule defines a second reporting period thatindicates when the first set of VR PM data is to be reported from theVNFM, wherein the one or more processors are configured to receive thefirst set of VR PM data from the VNFM according to the second VR PMschedule.

Example 41 comprises the subject matter of any variation of example 38,wherein the first VR PM schedule defines a first reporting period thatindicates when the second set of VR PM data is to be output by the EM,wherein the one or more processors are configured to output the secondset of VR PM data to the NM according to the first VR PM schedule.

Example 42 comprises the subject matter of any variation of any ofexamples 36-37, wherein the first set of VNF PM data is one of aplurality of sets of VNF PM data received from the VNF, wherein thesecond set of VNF PM data is based at least in part on each of theplurality of sets of VNF PM data.

Example 43 comprises the subject matter of any variation of any ofexamples 36-37, wherein the VNF PM job comprises a VNF PM schedule.

Example 44 comprises the subject matter of any variation of example 43,wherein the request to the VNF indicates to collect the first set of VNFdata according to the VNF PM schedule.

Example 45 comprises the subject matter of any variation of example 43,wherein the second set of VNF data is output to the NM according to theVNF PM schedule.

Example 46 comprises the subject matter of any variation of example 36,wherein the first VR PM job comprises a first VR PM schedule and thesecond VR PM job comprises a second VR PM schedule.

Example 47 comprises the subject matter of any variation of example 36,wherein the first set of VNF PM data is one of a plurality of sets ofVNF PM data received from the VNF, wherein the second set of VNF PM datais based at least in part on each of the plurality of sets of VNF PMdata.

Example 48 comprises the subject matter of any variation of example 36,wherein the VNF PM job comprises a VNF PM schedule.

Example 49 is an apparatus configured to be employed within a NetworkManager (NM), comprising one or more processors configured to: output arequest to a network Element Manager (EM) to create a VirtualizedNetwork Function (VNF) PM job to collect VNF Performance Measurement(PM) data; process a set of Virtualized Network Function (VNF)Performance Measurement (PM) data associated with a VNF, wherein the setof VNF PM data is received from the EM; make a determination whether theVNF has a negative performance issue, based on the processed set of VNFPM data; output a request to the EM to create a Virtualization Resource(VR) PM job to collect VR PM data from a VR used by the VNF, based on adetermination that the VNF has the negative performance issue; process aset of VR PM data received from the EM; make a determination whether torestart the VNF, based on the processed set of VR PM data and theprocessed set of VNF PM data; and output a request to a network functionvirtualization orchestrator (NFVO) to restart the VNF based on adetermination to restart the VR.

Example 50 comprises the subject matter of any variation of example 49,wherein the one or more processors are configured to make thedetermination whether the VNF has the negative performance issue basedon one or more comparisons between the set of VNF PM data and one ormore VNF PM thresholds.

Example 51 comprises the subject matter of any variation of any ofexamples 49-50, wherein the one or more processors are furtherconfigured to: analyze the set of VNF PM data and the set of VR PM data;make a determination whether an abnormal VR usage pattern is detectedbased on the analyzed set of VNF PM data and the analyzed set of VR PMdata; and make the determination whether to restart the VNF based on thedetermination being made that the abnormal VR usage pattern is detected.

Example 51 comprises the subject matter of any variation of example 49,wherein the one or more processors are further configured to: analyzethe set of VNF PM data and the set of VR PM data; make a determinationwhether an abnormal VR usage pattern is detected based on the analyzedset of VNF PM data and the analyzed set of VR PM data; and make thedetermination whether to restart the VNF based on the determinationbeing made that the abnormal VR usage pattern is detected.

Example 52 is an apparatus configured to be employed within a NetworkManager (NM), comprising means for processing configured to: generate aVirtualized Network Function (VNF) Performance Management (PM) jobassociated with a first VNF, wherein the VNF PM job comprises a VNF PMschedule; output a request to an Element Manager (EM) to create the VNFPM job; receive a set of VNF PM data from the EM according to the VNF PMschedule; generate a Virtualization Resource (VR) PM job comprising a VRPM schedule, wherein the VR PM job is associated with a VR of the VNF;output a request to the EM to create the VRM PM job; receive a set of VRPM data from the EM according to the VR PM schedule, make adetermination whether an abnormal VR usage pattern is present based onan analysis of the set of VNF PM data and the set of VR PM data; andoutput to a Network Function Virtualization Orchestrator (NFVO) arequest to restart the VNF based on a determination that the abnormal VRusage pattern is present.

Example 53 comprises the subject matter of any variation of example 52,wherein the means for processing are further configured to compare theset of VNF PM data to one or more VNF PM thresholds to determine whetherthe one or more VNF PM thresholds have been crossed, wherein the VR PMjob is generated based on a determination that at least one of the oneor more VNF PM thresholds has been crossed.

Example 54 comprises the subject matter of any variation of example 52,wherein the VR PM job indicates a resource type of the VR, a collectionperiod of the VR PM schedule, and one or more reporting periods of theVR PM schedule, wherein the set of VR PM data is received from the EM inaccordance with the one or more reporting periods.

Example 55 comprises the subject matter of any variation of any ofexamples 52-54, wherein the request to restart the VNF comprises arequest to terminate and re-instantiate the VNF.

Example 56 comprises the subject matter of any variation of any ofexamples 52-54, wherein the request to restart the VNF comprises arequest to reset the VNF.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the disclosed subject matter has been described inconnection with various embodiments and corresponding Figures, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

In particular regard to the various functions performed by the abovedescribed components or structures (assemblies, devices, circuits,systems, etc.), the terms (including a reference to a “means”) used todescribe such components are intended to correspond, unless otherwiseindicated, to any component or structure which performs the specifiedfunction of the described component (e.g., that is functionallyequivalent), even though not structurally equivalent to the disclosedstructure which performs the function in the herein illustratedexemplary implementations. In addition, while a particular feature mayhave been disclosed with respect to only one of several implementations,such feature may be combined with one or more other features of theother implementations as may be desired and advantageous for any givenor particular application.

What is claimed is:
 1. A method, for restoring performance of virtualnetwork functions (VNFs) of a wireless network, comprising: outputting arequest to a network Element Manager (EM) to create a VirtualizedNetwork Function (VNF) Performance Measurement (PM) job to collect VNFPM data from a VNF; receiving a set of VNF PM data associated with theVNF from the EM; processing the set of VNF PM data associated with theVNF; outputting a request to the EM to create a Virtualization Resource(VR) PM job to collect, through a VNF Manager (VNFM) and a virtualizedinfrastructure manager (VIM), VR PM data from a VR used by the VNF;receiving a set of VR PM data from the EM; and processing the set of VRPM data.
 2. The method of claim 1, further comprising: making adetermination, based on the processed set of VNF PM data, whether theVNF has a negative performance issue, wherein the request to the EM tocreate the VR PM job is based on a determination that the VNF has thenegative performance issue.
 3. The method of claim 2, furthercomprising: making the determination, based on one or more comparisonsbetween the set of VNF PM data and one or more VNF PM thresholds,whether the VNF has the negative performance issue.
 4. The method ofclaim 1, further comprising: analyzing the set of VNF PM data and theset of VR PM data; making a determination, based on the analyzed set ofVNF PM data and the analyzed set of VR PM data, whether an abnormal VRusage pattern is detected; and making a determination whether to restartthe VNF based on the determination being made that the abnormal VR usagepattern is detected.
 5. The method of claim 4, wherein the abnormal VRusage pattern comprises a processor usage below a processing thresholdand a memory usage above a memory threshold.
 6. The method of claim 1,further comprising: generating a VNF PM job associated with the VNF,wherein the VNF PM job comprises a VNF PM time period to execute; andoutputting a request to the EM to create the VNF PM job; wherein the setof VNF PM data is received from the EM based on the VNF PM time periodto execute.
 7. The method of claim 1, wherein the VR PM job designates aresource type that indicates the VR from which the VR PM data is to becollected.
 8. The method of claim 1, wherein the VR PM job designates acollection period that indicates when the VR PM data is to be collected.9. The method of claim 1, wherein the VR PM job designates one or morereporting periods that indicate when the VR PM data is to be reported toa network manager (NM).
 10. The method of claim 1, wherein the VR PM jobindicates one or more measurement types to be collected, wherein the setof VR PM data comprises data of the one or more indicated measurementtypes.
 11. The method of claim 1, wherein a determination to restart theVNF is made based on the processed set of VR PM data and the processedset of VNF PM data and is a determination to terminate andre-instantiate the VNF, and wherein a request to restart the VNF is sentto a network function virtualization orchestrator (NFVO) and is arequest to terminate and re-instantiate the VNF.
 12. The method of claim1, wherein a determination to restart the VNF is made based on theprocessed set of VR PM data and the processed set of VNF PM data and isa determination to reset the VNF, and wherein a request to restart theVNF is sent to a network function virtualization orchestrator (NFVO) andis a request to reset the VNF.
 13. An apparatus configured to beemployed for a network Element Manager (EM), comprising: a memory forstoring instructions; and one or more processors, when executing theinstructions, configured to: receive, from a Network Manager (NM), afirst Performance Measurement (PM) job related to a Virtualized NetworkFunction (VNF) for collecting VNF PM data, the first PM job comprisingmeasurement types, measured resources, and time period to execute andbeing associated with the VNF; collect the VNF PM data from the VNF;receive, from the NM, a second PM job related to Virtualization Resource(VR) for collecting VR PM data, the second PM job comprising measurementtypes, measured resources, and time period to execute and beingassociated with a VR of the VNF; output a request to a VNF Manager(VNFM) to create a PM job at the VNFM according to the second PM job;and collect the VR PM data from the VNFM.
 14. The apparatus of claim 13,wherein the instructions, when executed, further cause the EM to reportthe VNF PM data to the NM, wherein the VNF PM data is used to determinewhether to create the second PM job.
 15. A method, for restoringperformance of virtual network functions (VNFs) of a wireless network,comprising: receiving, from a Network Manager (NM), a first PerformanceMeasurement (PM) job for collecting PM data; processing the first PM jobat a network element manager (EM); and if the collecting PM data is forVirtualized Network Function (VNF) PM data collection, outputting arequest to a VNF to collect a first set of PM data based on the first PMjob; and receiving the first set of PM data from the VNF in response tothe request to the VNF; and if the collecting PM data is forVirtualization Resource (VR) PM data collection, creating a second PMjob at a VNF Manager (VNFM) to collect a second set of PM data, andreceiving the second set of PM data from the VNFM; and outputting to theNM the first set of PM data and the second set of PM data.
 16. Themethod of claim 15, wherein the first PM job and the second PM job eachindicate one or more measurement types to be collected, wherein each ofthe first and the second set of PM data comprises data of the one ormore indicated measurement types.
 17. The method of claim 15, whereinthe first PM job comprises a first time period to execute and the secondPM job comprises a second time period to execute, wherein the first timeperiod to execute and the second time period to execute each define acollection period that indicates when the PM data is to be collected.18. The method of claim 17, wherein the first set of PM data is used todetermine whether to create the second PM job.
 19. The method of claim15, wherein the first set of PM data is one of a plurality of sets ofVNF PM data received from the VNF.
 20. The method of claim 15, whereinthe first PM job comprises a VNF time period to execute.